Skip to main content

Process Monitoring

Monitoring and alarming a re two important functions that are important to guarantee a smooth service of Orchestra. Therefor the systems needs the capability to inform an administrator in case of errors ore problematic system states. Further more, Orchestra has to provide monitoring capabilities that allow to evaluate the current state of the systems. Within Orchestra technical we have to differentiate between technical monitoring, process monitoring and alarming.

Technical monitoring​

Technical monitoring relates to all system activities that are not directly associated with an executable process instance or errors that are of technical nature . Errors of such a category are network errors, database errors, security errors and so on. When ever such an error occurs, a system event is sent to the event subsystem. The event subsystem stores the event information in that database and an administrator can have a look with the integrated Orchestra monitor.

Alarming​

In case of an error or warning the system administrator has to be informed automatically. This is necessary since in case of an error a immediate reaction is necessary in order to support a continuous operation of Orchestra. The alarming component is also attached to the event subsystem. Whenever an system event of type error occurs an email can be sent to an administrator. The automatic notification by mail can be configured to sent one mail per error or to collect errors and sent one mail after a given time limit is reached.

The process monitoring allows the observation of all system activities that are related to the execution of a process. The following events are monitored for the execution of a process instance:

  • start and stop of a process instance

  • entry and leave of an activity within the process model

  • errors that occur in the context of an activity

  • Content of messages that are associated with a process instance